-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Requirements pertaining to storage #208
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a very useful clarification
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
This is great.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All good, just suggestions 👍
Co-authored-by: Ruben Verborgh <[email protected]>
Co-authored-by: Ruben Verborgh <[email protected]>
Co-authored-by: Ruben Verborgh <[email protected]>
Thanks Ruben! Noting here that I've also discussed some of these requirements with @timbl and it was agreed - although not the exact wording in this PR. Happy to revise. |
In response to the following (and possibly other) issues on the relationship between data pod and Storage, determining and discovering storage:
Special shoutout to @megoth and co sharing their implementation experience as well as documenting their findings: https://megoth.inrupt.net/public/SolidDataBrowser/pod-info.html ( https://web.archive.org/web/20201106145438/https://megoth.inrupt.net/public/SolidDataBrowser/pod-info.html ). More of this please! Thanks.